Update filterSrv.js #615
Closed
Update filterSrv.js #615
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
filter.from is already a valid elasticsearch date field
|
The reason we use parseDate is because there are other panels that need to know exact time range that was requested (eg, the histogram) to be able to correctly set their min and max points. Parsedate allows us to send the time as the browser sees it, instead of what the elasticsearch server thinks the time is. |
w33ble
pushed a commit
to w33ble/kibana
that referenced
this pull request
Sep 13, 2018
This was referenced Sep 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
filter.from is already a valid elasticsearch date field